Conversation
Co-authored-by: Mikael Simberg <mikael.simberg@iki.fi>
|
cscs-ci run |
|
cscs-ci run |
|
cscs-ci run default |
1 similar comment
|
cscs-ci run default |
|
test comment |
1 similar comment
|
test comment |
|
cscs-ci run default |
|
cscs-ci run |
|
cscs-ci run |
|
cscs-ci run |
There was a problem hiding this comment.
Pull request overview
Adds an initial CSCS CI “ci-ext” setup to build backend-specific container images via Spack and run CTest suites selected by labels.
Changes:
- Labeled CTest tests as
serialandparallel-ranks-<n>and adjusted MPI test registration logic. - Added CSCS CI pipeline definition to build deps/build images per backend and run labeled tests.
- Added Spack environment files and Containerfiles to install dependencies and build the project in CI containers.
Reviewed changes
Copilot reviewed 9 out of 9 changed files in this pull request and generated 7 comments.
Show a summary per file
| File | Description |
|---|---|
| test/CMakeLists.txt | Adds test labels and introduces an MPIEXEC fallback for parallel C++ tests. |
| test/bindings/fortran/CMakeLists.txt | Adds labels for Fortran parallel tests. |
| .cscs-ci/spack/ucx.yaml | Spack env for backend=ucx +cuda. |
| .cscs-ci/spack/nccl.yaml | Spack env for backend=nccl +cuda (currently unused in pipeline). |
| .cscs-ci/spack/mpi.yaml | Spack env for backend=mpi +cuda. |
| .cscs-ci/spack/libfabric.yaml | Spack env for backend=libfabric +cuda. |
| .cscs-ci/default.yaml | Defines CI jobs to build deps/build images and run labeled serial/parallel tests. |
| .cscs-ci/container/deps.Containerfile | Builds a deps image by concretizing/installing Spack dependencies. |
| .cscs-ci/container/build.Containerfile | Builds the project inside the deps image with backend-specific CMake options. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
I previously though test_cancel was occasionally flaky in CI, but after running more times I think that was completely wrong. I have still seen the parallel test jobs occasionally hang before any of the tests actually start running and after ctest has discovered tests (or while it's discovering tests). I currently have no explanation for this other than filesystem/network issues. If it continues being a problem I'll have to look closer at it, but at the moment I have no reason to believe it's the tests that are buggy. |
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 9 out of 9 changed files in this pull request and generated 9 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
No description provided.